Systems and methods for installing and wiring building equipment

ABSTRACT

Systems and methods for guided installation of building equipment are provided. A request for a wiring diagram for wiring a first piece of building equipment to a second piece of building equipment is received from a user device. One or more first wiring configurations associated with the first piece of building equipment and one or more second wiring configurations associated with the second piece of building equipment are identified. Based on the one or more first wiring configurations and the one or more second wiring configurations, an equipment-specific wiring configuration for wiring the first piece of building equipment to the second piece of building equipment is automatically selected. A graphical user interface including a wiring diagram illustrating the equipment-specific wiring configuration is provided to the user device.

BACKGROUND

The present disclosure relates generally to installing and wiringbuilding equipment. The present disclosure relates more particularly tosystems and methods for automatically generating and presenting wiringdiagrams to a user for use in installing and wiring building equipmentsuch as controllers and controllable equipment. The present disclosurerelates more particularly still to providing a graphical user interfacethat a user can see and use when installing and wiring buildingequipment.

Equipment installation personnel often need to install equipment inbuildings to control different aspects of the building. Examples ofcontrollable equipment in a building are sensors, valves, fans,lighting, and any other device that makes the building inhabitable. Tocontrol these devices, controllers are often installed and wired to thecontrollable equipment so the devices can be more easily controlled.Installing the controllers and the controllable equipment is oftencomplex so building owners call experienced installers to make sure theinstallation is done correctly. Even experienced installers use diagramsand data sheets to determine how to wire the controllers to the devices.

Typically, multiple wiring diagrams are needed to understand how toinstall a specific controller to a specific device (e.g., one wiringdiagram for the controller and another wiring diagram for the device).These diagrams are often generic representations of the wiring to commonlanguage which is not typically learned by the installer until aftermultiple years of training. For example, there may be multiple symbolsin a wiring diagram that a first time installer may not understand. Toadd to this problem, the wiring diagram may not pertain to the exactdevices being installed, and instead pertain just to a generic versionof the device, meaning the first time installer would need to bothdecipher the generic language wiring diagram and adjust for anydifferences between the specific model of the device and the specificmodel shown in the diagram. It would be desirable to provide wiringinstructions that overcome these and other disadvantages.

SUMMARY

One implementation of the present disclosure is a method for guidedinstallation of building equipment. The method comprises receiving, froma user device, a request for a wiring diagram for wiring a first pieceof building equipment to a second piece of building equipment andidentifying one or more first wiring configurations associated with thefirst piece of building equipment and one or more second wiringconfigurations associated with the second piece of building equipment.The method also comprises automatically selecting, based on the one ormore first wiring configurations and the one or more second wiringconfigurations, an equipment-specific wiring configuration for wiringthe first piece of building equipment to the second piece of buildingequipment and providing a graphical user interface to the user device,the graphical user interface comprising a wiring diagram illustratingthe equipment-specific wiring configuration.

In some embodiments, the first piece of building equipment is acontroller and the second piece of building equipment is a field device.

In some embodiments, the request comprises a first equipment identifieridentifying the first piece of building equipment and a second equipmentidentifier identifying the second piece of building equipment.

In some embodiments, the method further comprises obtaining the firstequipment identifier from the first piece of building equipment andobtaining the second equipment identifier from the second piece ofbuilding equipment. The first and second equipment identifierscomprising at least one of an RFID code, a UPC code, a CPC binary barcode, a POSTNET, or a QR code.

In some embodiments, the method further comprises receiving a secondrequest from the user device for new wiring configurations associatedwith the two pieces of building equipment based on an input from a userand configuring a new graphical user interface based on the new wiringconfigurations.

In some embodiments, the method further comprises sending all wiringconfigurations associated with the two pieces of building equipment,regardless of the request from the user device, after receiving therequest from the user device.

In some embodiments, the method further comprises tagging each of theone or more first wiring configurations with an identifier of the firstpiece of building equipment and tagging each of the one or more secondwiring configurations with an identifier of the second piece of buildingequipment.

In some embodiments, automatically selecting the equipment-specificwiring configuration comprises selecting a wiring configuration taggedwith both the identifier of the first piece of building equipment andthe identifier of the second piece of building equipment.

In some embodiment, identifying the wiring configurations comprisesidentifying, from a database comprising controller diagrams and adatabase comprising field device data, one or more wiring configurationsthat have been tagged with an identifier representing the first piece ofbuilding equipment and one or more wiring configurations that have beentagged with an identifier representing the second piece of buildingequipment.

In some embodiments, the method further comprises displaying, via theuser device, a user interface that prompts a user to select a firstwiring connection on the first piece of building equipment to wire to asecond wiring connection on the second piece of building equipment.Automatically selecting the equipment-specific wiring configurationcomprises selecting a wiring configuration in which the first wiringconnection on the first piece of building equipment is wired to thesecond wiring connection on the second piece of building equipment.

Another implementation is an installation management system for buildingequipment. The installation management system comprises one or moreprocessors communicatively coupled to one or more memory devices, saidinstallation management system is configured to receive, from a userdevice, a request for a wiring diagram for wiring a first piece ofbuilding equipment to a second piece of building equipment and identifyone or more first wiring configurations associated with the first pieceof building equipment and one or more second wiring configurationsassociated with the second piece of building equipment. The installationmanagement system is also configured to automatically select, based onthe one or more first wiring configurations and the one or more secondwiring configurations, an equipment-specific wiring configuration forwiring the first piece of building equipment to the second piece ofbuilding equipment and provide a graphical user interface to the userdevice, the graphical user interface comprising a wiring diagramillustrating the equipment-specific wiring configuration.

In some embodiments, the first piece of building equipment is acontroller and the second piece of building equipment is a field device.

In some embodiments, the request comprises a first equipment identifieridentifying the first piece of building equipment and a second equipmentidentifier identifying the second piece of building equipment.

In some embodiments, the installation management system is furtherconfigured to obtain the first equipment identifier from the first pieceof building equipment and obtain the second equipment identifier fromthe second piece of building equipment, the first and second equipmentidentifiers comprising at least one of an RFID code, a UPC code, a CPCbinary bar code, a POSTNET, or a QR code.

The installation management system of claim 11, wherein the installationmanagement system is further configured to receive a second request fromthe user device for new wiring configurations associated with the twopieces of building equipment based on an input from a user andconfiguring a new graphical user interface based on the new wiringconfigurations.

The installation management system of claim 11, wherein the installationmanagement computer system is further configured to tag each of the oneor more first wiring configurations with an identifier of the firstpiece of building equipment and tag each of the one or more secondwiring configurations with an identifier of the second piece of buildingequipment.

Another implementation is a non-transitory computer-readable storagemedium having computer-executable instructions embodied thereon, whereinwhen executed by at least one processor. The computer-executableinstructions cause the at least one processor to receive, from a userdevice, a request for a wiring diagram for wiring a first piece ofbuilding equipment to a second piece of building equipment and identifyone or more first wiring configurations associated with the first pieceof building equipment and one or more second wiring configurationsassociated with the second piece of building equipment. Thecomputer-executable instructions automatically select, based on the oneor more first wiring configurations and the one or more second wiringconfigurations, an equipment-specific wiring configuration for wiringthe first piece of building equipment to the second piece of buildingequipment and provide a graphical user interface to the user device, thegraphical user interface comprising a wiring diagram illustrating theequipment-specific wiring configuration.

In some embodiments, the first piece of building equipment is acontroller and the second piece of building equipment is a field device.

In some embodiments, the computer-executable instructions further causethe processor to obtain the first equipment identifier from the firstpiece of building equipment and obtain the second equipment identifierfrom the second piece of building equipment. The first and secondequipment identifiers comprise at least one of an RFID code, a UPC code,a CPC binary bar code, a POSTNET, or a QR code.

In some embodiments, the computer-executable instructions further causethe processor to tag each of the one or more first wiring configurationswith an identifier of the first piece of building equipment and tag eachof the one or more second wiring configurations with an identifier ofthe second piece of building equipment.

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting an example installation environmentfor configuring and displaying wiring diagrams for building equipment,according to some embodiments.

FIG. 2 is a block diagram of an installation management system 114 usedto generate user interactive graphical user interfaces displaying wiringdiagrams between two pieces of building equipment

FIG. 3 is a block diagram of an installation management system that canreceive requests for wiring diagrams from a user device, generate thewiring diagrams, and display the wiring diagrams via the user device,according to some embodiments.

FIG. 4 is flowchart of a process for uploading wiring diagrams andequipment data pertaining to building equipment to an installationmanagement system and sending and displaying them on a user device,according to some embodiments.

FIG. 5 is a wiring diagram illustrating various wiring configurationsfor an actuator, according to some embodiments.

FIG. 6 is an illustration of a user device with a graphical userinterface generated by the installation management system of FIGS. 2-4including wiring and configuration instructions for building equipment,according to some embodiments.

FIG. 7 is another illustration of a user device with a graphical userinterface generated by the installation management system of FIGS. 2-4including wiring and configuration instructions for building equipment,according to some embodiments.

FIG. 8 is an illustration of a wiring diagram of a controller connectedto a field device, according to some embodiments.

FIG. 9 is an illustration of a user device connected to a productdatabase having a wiring configuration connecting a controller with afield device, according to some embodiments.

DETAILED DESCRIPTION

Overview

Referring generally to the figures, a system and method forautomatically generating and presenting wiring instructions for buildingequipment are shown, according to various exemplary embodiments. Aninstallation management system may be able to receive, store, and createinteractive graphical user interfaces including wiring diagrams forbuilding equipment and data associated with the building equipment. Thebuilding equipment may be a controller or other types of devicesconfigured to operate buildings. In some embodiments, the installationmanagement system creates the graphical user interface in response toreceiving a request from a user device. The request may ask for a wiringdiagram and/or data associated with building equipment. The wiringdiagram and the data may be shown in combination to provide instructionsat the user device showing how to wire two or more pieces of buildingequipment.

The installation management system may include a serving system. Theserving system may be able to receive and process building equipmentinformation (e.g., wiring diagrams, configuration information, etc.)received from controller providers and field device providers and storethe information in a database. The serving system may be able toconfigure controller information before storing the information in acontroller database so the controller information and the dataassociated with it is easily accessible when being retrieved. Theserving system may also store information associated with field devicesin a field device database.

The installation management system may also include a wiring diagramgenerator that can interact with user devices through a serving systemto respond to requests sent from the user devices when users interactwith a graphical user interface on the user device. The wiring diagramgenerator may be able to retrieve controller information from thecontroller database and data associated with field devices from a fielddevice database. The wiring diagram generator may then automaticallygenerate a graphical wiring diagram showing each piece of buildingequipment wired together and send the graphical wiring diagram to a userinterface generator.

The wiring diagram generator may automatically generate a graphicalwiring diagram by generating a list of possible wiring configurationsfor each piece of building equipment. Each list can have one or morewiring configurations. The wiring diagram generator can then match thewiring configurations of each piece of building equipment together toform a list of possible wiring configurations and generate a graphicalwiring diagram based on the list. After the graphical wiring diagram isgenerated, the wiring diagram generator can send it to the userinterface generator.

A user interface generator may be included in the installationmanagement system. The user interface generator may be configured tocreate a user interactive graphical user interface including thegraphical wiring diagram it receives from the wiring diagram generator.After generating a graphical user interface with this data, the userinterface generator may be able to send the graphical user interface tothe user device. Users may be able to press on the graphical userinterface to ask for different information in the graphical userinterface, at which point the user interface generator may receive a newgraphical wiring diagram from the wiring diagram generator, generate anew user interface with the graphical wiring diagram, and send the newuser interface to the user that made the request.

To generate a request for a graphical user interface, a user may use auser device to input two specific types of building equipment to theinstallation management system. The request may include an identifierdescribing a type of of building equipment. In some embodiments the usermay input the controller and building equipment by manually typing inproduct codes associated with the device, scanning an RFID code, a UPCcode, a CPC binary bar code, a POSTNET, a QR code, etc. The user mayinput one or a plurality of pieces of building equipment to obtaininformation about each piece of building equipment and how to wire themtogether.

In an example of the installation management system generating a wiringdiagram between two pieces of building equipment, a user may scan anRFID code for a standard controller and an RFID code for an actuator.The user may then send a request through a user device to theinstallation management system asking the installation management systemfor information about how to wire the controller to the actuator. Theinstallation management system may search the databases and generate agraphical user interface to send back to the user device showing optionsfor how the actuator and controller should be wired. The user may beable to input a configuration selection and send a request back to theuser interface generator asking for more specific information about thedesired wiring configuration. The installation management system mayreceive the request, retrieve the associated data, and then send agraphical user interface showing the desired wiring configuration. Insome embodiments, the user can press on a component within the graphicaluser interface to adjust the wiring configuration to change how theactuator operates, such as rotating clockwise instead of counterclockwise. The request may be sent to the installation managementsystem, which again may retrieve the data from the databases and sendback a graphical user interface with the data pertaining to a new wiringconfiguration.

Advantageously, the systems and methods described herein may be able tohelp speed up installation and make the installation process easier byidentifying a specific controller and a field device, or other specificcomponents and providing device-specific wiring diagrams for theidentified devices. Thus, a more descriptive wiring diagram andinstallation information may be obtained. Through the use of producttagging, such as UPC, QR codes, RFID, etc., each product could beuniquely identified and the device identity information could beprovided via a device, e.g. mobile phone, tablet, etc. A personinstalling a controller to the field device may be able to easilydetermine how to install the specific controller with the specificdevice on hand instead of guessing how to wire the field device to thecontroller based on specialized symbols and generalized wiring diagrams.Further, the data associated with the field device may be integratedwith the controller information so an installer may be able to easilysee how to install the controller with the field device. In someembodiments, if the installer needs to know how to change the operationof field device or needs to change the device configuration, the presentdisclosure provides an easy method of doing so.

It is understood that the installation management system may be readilyimplemented in various types of controllers (e.g., motor controllers,power controllers, fluid controllers, HVAC controllers, lightingcontrollers, chemical controllers, process controllers, etc.) andvarious types of control systems (e.g., closed-loop control systems,open-loop control systems, feedback control systems, feed-forwardcontrol systems, etc.) as may be suitable for various applications. Allsuch implementations should be considered within the scope of thepresent disclosure. It is also understood that the invention is notlimited to the details or methodology set forth in the description orillustrated in the figures. The terminology used in the presentdisclosure is for the purpose of description only and should not beregarded as limiting.

Installation Environment

Referring now to FIG. 1 , a diagram depicting an installationenvironment 100 for generating and displaying instruction diagrams withfield devices is shown, according to some embodiments. Installationenvironment 100 is shown to include a controller provider 102, a fielddevice provider 104, user devices 106, 108, and 110, and an installationmanagement system 114 all connected to each other via a network 115.Each of the components 102, 104, 106, 108, 110, and 114 may beimplemented or associated with hardware, software, or firmware, or anycombination thereof. For example, elements 102, 104, 106, 108, 110, and114 may be implemented using servers, software processes, and/orembedded systems. User devices 106, 108, and 110 are used by end users,such as installers, as described below.

In brief overview, a controller provider 102 and a field device provider104 may provide device information (e.g., configuration information,wiring diagrams, device specifications, etc.) for various types ofcontrollers and field devices. The device information may be stored in afield device database 120 and a controller database 122 and can beaccessed by installation management system 114. A user wishing to wiretwo or more pieces of building equipment together may provide a requestfor installation instructions to installation management system 114 viaone or more of user devices 106-110. The request may include deviceidentifying information (e.g., device model numbers, an image of thepieces of building equipment, an image of an RFID code, a UPC code, aCPC binary bar code, a POSTNET, or a QR code on the pieces of buildingequipment, etc.) that allows installation management system 114 toidentify the two or more pieces of building equipment that the userwishes to wire together. Installation management system 114 mayautomatically identify the pieces of building equipment and retrieve thecorresponding device information from field device database 120 and/orcontroller database 122. Installation management system 114 may use thedevice-specific information to automatically generate a wiring diagramthat is specific to the identified pieces of building equipment.Installation management system 114 may provide the wiring diagram touser devices 106-110 as part of a graphical user interface. The user maybe able to then use the device-specific wiring diagram to wire the twoor more pieces of building equipment together.

Controller provider 102 may include any entity that generates anduploads different controller information, which may include, but is notlimited to, wiring diagrams, configuration information, devicespecifications, installation instructions, and other information relatedto controllers, onto network 115. The entity could be, but is notlimited to, a controller designer, manufacturer, distributor, installer,or another entity that creates provides, or maintains informationassociated with various types of controllers. Controller provider 102may design different types of controllers, such as, but not limited toproportional controllers, derivative controllers, integral controllers,PID controllers, and any other type of controller. Controllerinformation may be described with pictures, words, sounds, or anycombination thereof.

Controller database 122 may be a dynamic database including controllerinformation, wiring diagrams, and other data associated with controllersuploaded to network 115 by controller provider 102. Controller database122 may hold any amount of controller information and wiring diagrams.Controller database 122 may be organized into sections. Each sectionrepresents a different type of building equipment. The sections may thenbe further broken down into subsections, wherein each subsection canrepresent specific types of the field devices or specific models of thefield devices. Wiring diagrams for specific models of the field devicemay be included in the subsection for specific types of field devices.Wiring diagrams may be added to controller database 122 by controllerprovider 102 at any time.

Different types of controllers that controller database 210 hasinformation about and that are included in controller database list 211include, but are not limited to, Metasys, FX PEAK, Simplex, and C-Cure.Different types of inputs that are included in controller database list211 include, but are not limited to, analog, binary, and universal.Different types of outputs that are included in controller database list211 include, but are not limited to, analog, binary, and configurable.These sections within controller database 210 are dynamic, so sectionsmay be added, sections may be removed, information may be added, andinformation may be removed.

Wiring diagrams may be removed by a user that attaches a machine tonetwork 115 and manually removes wiring diagrams from controllerdatabase 122 that are obsolete, incorrect, or no longer useful. The usermay remove wiring diagrams for any other reason. Another method ofremoving wiring diagrams from controller database 122 is setting up anautomatic removal system, where any wiring diagrams that have been incontroller database for X years are automatically removed. X may be ableto be any number of years, including a portion of a year. There are nolimitations to the amount of wiring diagrams controller database 122 mayhold or remove.

Field device provider 104 may include any entity that generates anduploads data associated with one or a plurality of field devices ontonetwork 115. Similar to controller provider 102, field device provider104 may include any sort of entity. The entity could be, but is notlimited to, a field device designer, manufacturer, distributor,installer, or another entity that creates provides, or maintainsinformation associated with various types of controllers. The data thatfield device provider 104 uploads to network 115 may describe fielddevices, how the field devices operate, and how to wire controllers tothe field devices. Examples of types of field devices may include, butare not limited to, actuators, pumps, fans, chillers, heaters, valves,air handling units, dampers, sensors, controllers, manufacturingdevices, or any other type of field device that may be able to be usedto monitor and/or control a building. The types may go into furthersubtypes for different models of each type of field devices.

The data provided by field device provider 104 may include detaileddrawings of the field devices that show inputs where wires may beinserted into the field device and different functions that areassociated with each input. For example, if an actuator is the fielddevice, three inputs could be shown where wires could be inserted. Eachinput may have a designation for the wires labelling one input aspositive, one input as negative, and one input as neutral. If wiresgiving power are fed into the inputs, wherein the positive power wire isfed into the negative input and the negative wire is fed into thepositive input, a rotor in the actuator could rotate clockwise. However,if the wires are placed into the actuator in reverse, the rotor couldturn counter clockwise. These designations in the actuator could bearranged in any manner. Field device provider 104 may upload the inputsand all information about the inputs as data onto network 115. Otherexamples of data associated with one or a plurality of field device mayinclude attributes describing how the field device operates, similardevices, descriptions of how to connect wires to the respective fielddevice, warning signals, or any other information that could beassociated with the building equipment.

Field device provider 104 may also generate and upload schematics forfield devices to network 115. Schematics may be drawings that depictfield devices as separate components, descriptions of those components,and descriptions of how to connect the components together to create thefield device. Schematics may generally be used by installers when theinstallers are building a field device, such as a heater, in a space.The installers may look at the schematics and build the field devicesbased on the drawings and descriptions in the schematics.

Field device database 120 may be a dynamic database that includes dataassociated with different field devices provided by field deviceproviders 104, such as wiring diagrams. When field device provider 104uploads data concerning devices to network 115, the data may be storedin field device database 120. Field device database 120 may be able tohold any number of pieces of data pertaining to field devices. Data infield device database 120 may be organized into sections. Each sectionmay represent a different type of device, such as an actuator. Thesections may then be further broken down into subsections. Continuingwith an actuator as an example, the section with information aboutactuators can have further sections with specific types of actuatorsand/or specific models of actuators. Field device database 120 may beable to include any sort of data about the devices, including, but notlimited to, different wiring configurations, information about a motorin the device, information about the general specifications of thedevice, information concerning how a piece of building equipment worksand its benefits, information on how the piece of building equipment isoperated, information about how to assemble the device, informationabout warnings associated with the device, or any other pieces ofinformation associated with the building equipment

In some embodiments, field device database 120 is divided into aplurality of sections including, but not limited to, data associatedwith actuators, cameras, meters, sensors, smoke detectors, and any otherbuilding equipment that controllers may be wired to. Examples ofdifferent types of actuators include, but are not limited to,proportional, incremental, and two position. Examples of different typesof sensors include, but are not limited to, temperature, humidity,status, and CO2. Information in field device database 120 may bedynamic, so sections can be added, section may be removed, informationmay be added, and information may be removed.

Data concerning each piece of building equipment may also be removed if,for example, a user determines the data is obsolete, incorrect, or nolonger useful. The data may be removed for any reason. To remove thedata, a user could attach a machine to network 115 and access fielddevice database 120. Once the user accesses field device database 120,the user may be able to remove the data through the machine. Anothermethod of removing data from field device database 120 may be setting upan automatic removal system, where all data that has been in fielddevice database for X years is automatically removed. X may be anynumber of years, including a portion of a year. There are no limitationsto the amount of data field device database 120 may be able to hold orremove.

Field device provider 104 and controller provider 102 may be the sameentity. The entity may upload data to network 115 at the same time theentity uploads wiring diagrams 115 or it may upload them separately.

Referring still to FIG. 1 , user devices 106, 108, and 110 are shown.User devices 106, 108, and 110 may be electronic devices wherein usersmay be able to receive data and information from network 115. Userdevices 106, 108, and 110 may be able to send requests across network115 to installation management system 114 asking for data and wiringdiagrams about individual components. After sending the request, userdevices 106, 108, and 110 receive a graphical user interface from userinterface generator 112 in installation management system 114 with theinformation in a display for the user. Examples of user devices include,but are not limited to, mobile phones, electronic tablets, laptops,desktop computers, televisions, cameras, meters, sensors, smokedetectors, and any other electronic device that may be able to attach toa network. User devices 106, 108, and 110 may display data andinformation. User devices 106, 108, and 110 may receive and show datarelated to controller information sent to network 115 by controllerprovider 102 and data sent to network 115 by field device provider 104.According to the disclosure, user devices 106, 108, and 110 may be usedby installers using controller information sent by controller provider102 and/or data sent from field device provider 104 to install fielddevices, as described below. However, any type of entity may use userdevices 106, 108, and 110 and the controller information and data sentto user devices 106, 108, and 110. There may be any number of userdevices 106, 108, and 110 attached to network 115.

As will be described below, once the data and wiring diagrams are sentto user devices 106, 108, and 110, the data and controller informationmay be displayed to a screen on each user device 106, 108, and 110. Thedata and controller information may be shown adjacent to each other atone moment in time or separately.

In some embodiments, installation management system 114 is a system thatreceives, stores, and manipulates the data and wiring diagrams thatcontroller provider 102 and field device provider 104 send to network115. Installation management system 114 may also generate a graphicaluser interface and send the graphical user interface to user devices106, 108, and 110. Installation management system 114 may include anynumber of components for receiving, storing, and manipulating data andfor generating a graphical user interface. Installation managementsystem 114 may send the graphical user interface to user devices 106,108, and 110 via network 115. Installation management system 114 mayinclude a user interface generator 112, a wiring diagram generator 116,a serving system 118, a field device database 120, and a controllerdatabase 122. Each component 112, 116, 118, and 120 may be connected.Installation management system 114 may be connected to network 115through serving system 118.

Serving system 118 may be configured to receive requests from userdevices 106, 108, and 110, transmit the requests to wiring diagramgenerator 116, and send responses received from user interface generator112 to user devices 106, 108, and 110. For example, serving system 118can receive a request from a user device asking for a wiring diagramshowing a controller wired to a field device. Serving system 118 cansend the request to wiring diagram generator 116 and receive a userinterface from user interface generator 112. After receiving the userinterface from user interface generator 112, serving system 118 maydetermine if the user interface includes everything the requests asksfor. To do so, serving system 118 may compare the request with thecontents of the user interface. If the user interface includeseverything requested in the request, serving system may send the userinterface to network 115. If the user interface does not includeeverything, serving system 118 may send another request to wiringdiagram generator 116 with instructions to include more data from fielddevice database 120 or data from controller database 122. In thisscenario, wiring diagram generator 116 may retrieve the extra data orwiring diagrams and send a new graphical wiring diagram to userinterface generator 112. User interface generator 112 may create a newgraphical user interface and send it to serving system 118. Once servingsystem 118 verifies that everything asked for in the request has beenincluded in the user interface, serving system 118 may send the userinterface to network 115.

Serving system 118 can also be configured to receive and depositcontroller diagrams and field device wiring diagrams along withassociated data from controller provider 102 and field device provider104. After receiving the wiring diagrams and data, serving system 118can configure the wiring diagrams and data into a standardized form anddeposit them into databases 120 and 122.

Wiring diagram generator 116 may be configured to automatically generategraphical wiring diagrams and information associated with the wiringdiagrams and send them to user interface generator 112. Wiring diagramgenerator 116 may include any number of components and is not limited towhat is described here. Wiring diagram generator 116 may receive arequest from a user device 106, 108 or 110 through serving system 118requesting a graphical wiring diagram showing how to wire a controllerto a field device. The request may include an identifier representingpieces of building equipment, such as a controller and a field device.In some embodiments, the request could identify two controllers or twofield devices. Wiring diagram generator 116 may generate a wiringconfiguration list after determining the different wiring configurationsthat are compatible with both the controller and the field device.Wiring diagram generator 116 may then automatically select a wiringconfiguration from the wiring generation list. In some embodiments,wiring diagram generator 116 may automatically select the wiringconfiguration after receiving a request from a user identifying adesired mode of operation and selecting the wiring configuration thatallows the pieces of building equipment to operate in that mode. Afterselecting the wiring configuration, wiring diagram generator 116 may usethe selection to create a graphical wiring diagram and send thegraphical wiring diagram to user interface generator 112.

User interface generator 112 can be configured to receive the graphicalwiring diagram from wiring diagram generator 116 and generate agraphical user interface that shows how to wire two pieces of buildingequipment together. The graphical user interface may includedevice-specific wiring diagrams for connecting the two pieces ofbuilding equipment specified by the request to serving system 118. Thegraphical user interface may also contain information describing how towire the requested pieces of building equipment and may includedifferent wiring variations that each produce different modes ofoperation of the field device and/or controller. After generating thegraphical user interface, user interface generator 112 may send thegraphical user interface to user devices 106, 108, and 110 throughserving system 118 and network 115.

Network 115 may include any element or system that enables communicationbetween field devices and systems. Network 115 may enable communicationbetween controller provider 102, field device provider 104, user devices106, 108, and 110, user interface generator 112, and installationmanagement system 114 and its components therein. Network 115 mayconnect the components through different telecommunications networks,such as the Internet, Wi-Fi, telephone, Lan-connections, or any othernetwork that allows devices to communicate with each other. In someinstances, network 115 may include servers or processors that facilitatecommunications between the components of installation environment 100.

Referring now to FIG. 2 , a block diagram of an installation managementsystem 114 used to generate user interactive graphical user interfacesdisplaying wiring diagrams between two pieces of building equipment.System 114 is shown to include many of the same components describedwith reference to FIG. 1 . For example, system 114 is shown to include auser interface generator 112, a wiring diagram generator 116, a servingsystem 118, a field device database 120, and a controller database 122.System 114 may also include a wireless gateway 208, which may beconnected to user interface generator 112, wiring diagram generator 116,serving system 118, and databases 120 and 122. Installation managementsystem 200 may include additional, fewer, or different componentsdepending on the particular embodiment. Wireless gateway 208 may beconnected to user interface generator 112, wiring diagram generator 116,serving system 118, field device database 120, and controller database122 through a network (not shown).

Serving system 118 may be able to send and receive data and informationfrom the network or other components within installation managementsystem 114. Serving system 118 may be able to receive controllerinformation from controller providers 102 and distribute the controllerinformation to controller database 122. Serving system 118 may also beable to receive the data associated with a field device from fielddevice providers and distribute the field device data to field devicedatabase 120. In some embodiments, serving system 118 may also receiveuser interfaces from user interface generator 112. Once serving system118 receives a user interface, serving system 118 may be able totransmit the user interface to a user device (not shown). Further,serving device 118 may receive a request for data from the user device.After receiving the request, the serving system may transmit the requestto user interface generator 112.

Wiring diagram generator 116 is shown to include a building equipmentlocator 201, a controller identifier 202, a field device wiringidentifier 204, and a wiring configuration generator 206. Each componentin wiring diagram generator 116 may be connected to each other and towireless gateway 208. Components 201, 202, 204, and 206 can beconfigured to receive a request from a user device asking for a wiringdiagram between a controller and a field device, identify the controllerand field device in one or a plurality of databases, and determine whichwiring configuration will wire the controller to the field device. Thefollowing paragraphs describe some of the general functions performed byeach component 201, 202, 204, and 206 in wiring diagram generator 116.

Building equipment locator 201 may be a component within wiring diagramgenerator 116 configured to identify the pieces of building equipment auser wants to wire together based on information in a request withincontroller database 122 and field device database 120. For example, oncea user sends a request to wiring diagram generator 116 asking for awiring configuration between a controller and a field device, buildingequipment locator 201 can identify the controller and the field devicein the controller database and the field device database. Buildingequipment locator 201 can do this by matching a an RFID code, a UPCcode, a CPC binary bar code, a POSTNET, a QR code, or other type ofdevice-identifying information with a particular type of device (e.g., aparticular model) using the information in the controller database andfield device database. Consequently, the two “wiring identifier”components (controller identifier 202 and field device identifier 204)may know which wiring configurations to retrieve.

Controller identifier 202 may be a component within wiring diagramgenerator 116 configured to identify all of the possible wiringconfigurations that the identified controller is capable of using.Controller identifier 202 may be capable of using controller informationin controller database 122 to identify all possible wiringconfigurations that the controller could possibly use. For example, if arequest comes in asking how to wire a certain controller with a certainfield device, controller identifier 202 can retrieve information fromcontroller database 122 pertaining to the controller that buildingequipment locator 201 identified. Controller identifier 202 can sortthrough all of the information related to the controller and determineeach possible wiring configuration the controller has. Controlleridentifier 202 can send each possible wiring configuration to wiringconfiguration generator 206 along with data associated with each wiringconfiguration indicating how the controller operates under each wiringconfiguration.

Field device identifier 204 may be a component within wiring diagramgenerator 116 configured to identify all of the possible wiringconfigurations that the identified field device is capable of using.Controller identifier 202 may be capable of using field deviceinformation in field device database 120 to identify possible wiringconfigurations that the field provider could possibly use. Similar tocontroller identifier 202, field device identifier may be capable ofusing field device information in field device database 120 to identifyall possible wiring configurations that the field device could possiblyuse. Using the example above, field device identifier 204 can retrieveinformation from field device database 120 pertaining to the fielddevice that building equipment locator 201 identified. Field deviceidentifier 204 can sort through all of the information related to thefield device and determine each possible wiring configuration the fielddevice has. Field device identifier 204 can send each possible wiringconfiguration for the field device to wiring configuration generator 206along with data associated with the field device indicating how thefield device operates under each wiring configuration.

Wiring configuration generator 206 may be a component within wiringdiagram generator 116 configured to receive all of the possible wiringconfigurations from controller identifier 202 and field deviceidentifier 204. Wiring configuration generator 206 may also determinewhich wiring configurations are compatible with each other. Wiringconfiguration generator 206 may generate a list including each possiblewiring configuration that could be used to connect the identifiedcontroller to the identified field device. Wiring configurationgenerator 206 may generate this list by comparing the wiringconfigurations of the controller with the wiring configurations of thefield device and identifying wiring configurations in the controller andthe field device that are compatible with each other. In someembodiments, each matched wiring configuration corresponds to adifferent mode of operation for at least one of the controller and thefield device. For example, a request may be sent to wiring generator 206from a user device asking for a wiring diagram describing how to wire anactuator to a controller. Wiring configuration generator 206 can receiveall the possible wiring configurations of the controller and theactuator from controller identifier 202 and field device identifier 204respectively and generate a list of wiring configurations that cansuccessfully wire the actuator to the controller. After creating thelist, wiring configuration generator 206 can send the list to graphicalwiring diagram generator 207.

In some embodiments, wiring configuration generator 206 can identify awiring configuration between a specific controller and a specific fielddevice that causes the controller and field device to operate in aspecific manner. For example, if a user sends a request to wiringconfiguration generator 206 asking how to wire a controller to anactuator so the actuator rotates clockwise, wiring configurationgenerator 206 can identify and generate a wiring configuration that willcause the actuator to do so. Wiring configuration generator 206 maytailor the wiring configurations it generates to any sort of requestedmode of operation (e.g., low power, high power, clockwise,counterclockwise, pulse, continuous, etc.).

Graphical wiring diagram generator 207 may be a component within wiringdiagram generator 116 configured to create a graphical wiring diagram.The generated graphical wiring diagram may illustrate wiringconfigurations that allow both a controller and a field device tooperate properly when they are wired together. The graphical wiringdiagram may display any sort of information (e.g., descriptions of thecontroller, descriptions of the field device, possible wiringconfigurations between the two pieces of building equipment, warningsabout the pieces of building equipment, etc.) The graphical wiringdiagram may display wiring configurations in multiple ways (e.g., 3dimensional view, view from the top, the wiring configurations of thecontroller and the field device side by side, verbal instructions,etc.). In some embodiments, graphical wiring diagram generator 207 cangenerate a graphical wiring diagram including one or a plurality ofwiring configurations for a single controller or field device. Ifgraphical wiring diagram generator 207 determines that it needs moreinformation to create the graphical wiring diagram, it can send arequest back to components 201, 202, 204, and 206 asking for theinformation and generate a graphical wiring diagram based on thisinformation. Once graphical wiring diagram generator 207 generates thegraphical wiring diagram, graphical wiring diagram generator 207 cansend the graphical wiring diagram to user interface generator 112.

In some embodiments, graphical wiring diagram generator 207 can receiverequests from a user device through serving system 118 and requestinformation from components 201, 202, 204, 206 to respond to the requestfrom the user device. The request may be for different ways to wire thecontroller with the field devices, or it may be for a wiringconfiguration so the field device may operate in a specific manner.Graphical wiring diagram generator 207 may receive the request when auser wants to view a different wiring configuration than what wasinitially presented to the user. In this scenario, graphical wiringdiagram generator 207 can receive the request and update the graphicalwiring diagram with the new information it receives from components 202,202, 204, and 206.

Wireless gateway 208 may connect user interface generator 112, servingsystem 118, field device database 120, and controller database 122 tothe network and the components that are also attached to the network.Wireless gateway 208 may communicate with each processor that isinternal or external to the network using NFC, Bluetooth, WiFi direct,cables, etc., or via a communication network such as a BACnet network, aLonWorks network, a LAN, a WAN, the Internet, a cellular network, etc.using wired or wireless electronic data communications. User interfacegenerator 112 may be configured to retrieve a graphical wiring diagramfrom graphical wiring diagram generator 207 and generate a graphicaluser interface. User interface generator 112 may be one or a pluralityof components that are used to receive, configure, and distributegraphical user interfaces. After retrieving or receiving a graphicalwiring diagram from wiring diagram generator 116, user interfacegenerator 112 may be able to manipulate the graphical wiring diagram tocreate a user-interactive graphical user interface showing how to wire acontroller to a field device. User interface generator 112 may then beable to send the user an interactive graphical user interface includingdata associated with the controller and field device that are wiredtogether in the graphical wiring diagram.

An example graphical user interface generated by user interfacegenerator 112 is a picture of an actuator with inputs in the actuatorcolored differently from the rest of the actuator. The graphical userinterface may include a wiring diagram represented by wires going intothe inputs in a configuration and a description of the mode of operationfor the displayed wiring configuration. In some embodiments, thegraphical user interface is user-interactive, so a user may be able topress on different parts of the data or wiring diagrams to receive adifferent display. For example, if the graphical user interface isshowing an actuator wired so the rotor turns clockwise, the user may beable to press on the display and change the wiring to see how a changein wiring affects how the actuator operates. After changing the wiringin the graphical user interface, text may accompany the change tellingthe user the effect of the change. If a user asks for information thatis not included in the user interface, wiring diagram generator 116 maysend a new graphical wiring diagram to user interface generator 112 withthe requested data. User interface generator 112 may then create andsend a new graphical user interface to the user device that requestedthe new information. Once user interface generator 112 receives theinformation, user interface generator 112 may send the information tothe user device to display the information through the graphical userinterface.

In some embodiments, the graphical user interface is configured to senda request to components 201, 202, 204, 206, 207, and 112 after the userdevice sends a request to serving system 118 for a different wiringconfiguration between a controller and a field device or for moreinformation about a controller or field device. Components 201, 202,204, 206, 207, and 112 may retrieve the requested data, send a graphicalwiring diagram to user interface generator 112, and user interfacegenerator 112 can generate a new interactive user interface to send tothe user device.

In some embodiments, the information that user interface generator 112sends to the user device along with the graphical user interface alreadyincludes all possible connotations of requests from the user. Eachconfiguration is stored on the user device. Consequently, the graphicaluser interface can generate a new display showing newly requestedinformation by retrieving the new information from the user device. Userinterface generator 112 may send any number of wiring diagrams or datato a user device with a user interface, regardless of the request fromthe user device.

In some embodiments, a user device may request a wiring configurationbetween two controllers or two field devices. To do so, a user at a userdevice may input the product codes for two controllers or two fielddevices instead of a controller and a field device.

In some embodiments, serving system 118 can tag information associatedwith pieces of building equipment, such as controllers and fielddevices, with tags describing what type of controller and/or fielddevice they are, how they operate, and the different wiringconfigurations they have. In some embodiments, the entity uploading adiagram for a piece of building can manually tag the relevant equipmentand wiring diagram. In some embodiments, serving system 118 canautomatically tag the diagram with the building equipment's type byanalyzing the information on the diagram and determining which type ofbuilding equipment the information is describing by comparing theinformation to information in a database (not shown) full of buildingequipment types. If serving system 118 can find a match by findingenough similarities between the uploaded information and the informationin the database to meet a user selected threshold, serving system 118can tag the information indicating which piece of building equipment theinformation is describing.

Wiring configurations can be tagged with an identifier representingwhich controller or field device the wiring configuration can work withalong with the controller or field device's type. Once the wiringconfigurations are tagged, they can be stored in either database 120 or122. A wiring configuration can have multiple tags, each tagrepresenting a different type of field device or controller that canoperate with the wiring configuration. Further, each wiringconfiguration can have a tag of its own describing what type of wiringconfiguration it is and how it is meant to operate. An example is awiring configuration may be intended to cause an actuator to operateclockwise instead of counter clockwise, or at a variable speed insteadof a fixed speed. After tagging the devices and wiring configurations,serving system 118 can store the information about the devices incontroller database 122 and field device database 120. Upon receiving arequest from a user device, wiring diagram generator 207 can receivethese tags associated with the controllers and field devices andgenerate wiring diagrams by matching similarly tagged wiringconfigurations of the requested building equipment. In some embodiments,wiring diagram generator 207 can automatically generate the wiringdiagrams by selecting a wiring diagram that has been tagged withidentifiers for the requested building equipment.

Referring now to FIG. 3 , a block diagram of an installation managementsystem that can receive requests for wiring diagrams from a user device,generate the wiring diagrams, and display the wiring diagrams via theuser device is shown, according to some embodiments. The components ofsystem 300 may be similar to the components of installation environment100, described in reference to FIG. 1 , and the components of system200, described in reference to FIG. 2 . System 300 may includeadditional, fewer, or different components depending on the particularembodiment. System 300 may include an interface 302 displayed on a userdevice, wireless gateway 208, controller database 122, field devicedatabase 120, user interface generator 112, an interface 312, aninterface 316, and an interface 318. After an input from a user andthrough the user device, interface 302 may send wiring diagram generator116 requests to installation management system 114 including productcodes for controllers, field devices, or a combination of a controllerand a field device. After receiving a response to the request, interface302 may transition to interface 312. Interface 312 may send a request towiring diagram generator 116. In response, user interface generator 112may send a user device a graphical user interface to be displayed as anoutput represented by interface 316 or interface 318.

Interface 302 may be a graphical user interface that is shown on a userdevice. Interface 302 may be shown on any type of user device such as,but not limited to, personal computers (e.g., desktop computers), mobilecomputing devices, cell phones, smart phones, head-mounted computingdevices, media players/recorders, music players, game consoles, mediacenters, media players, electronic tablets, personal digital assistants(PDAs), television systems, audio systems, radio systems, removablestorage devices, navigation systems, set top boxes, and other electronicdevices. Interface 302 may include a request 301 asking for a user toinput a first product code, a request 303 asking the user to input asecond product code, and a next button 305 which brings the user to adifferent display on the graphical user interface. The interface may bedirected to allowing a user to input two different pieces of buildingequipment, such as, but not limited to, a controller and a field device,two controllers, or two field devices. The user may be able to inputboth product codes and then press the next button to obtain options forhow the user wants the graphical user interface to display the results.

Request 301 may be a request for the user to input a product code for atype of piece of building equipment the user wants information about.Request 301 may be asking for data associated with a device, dataassociated with controller information, data associated with acontroller, or data associated with any other type of buildingequipment. The user may respond to request 301 by manually typing outthe name of the piece of building equipment or by typing out a codeassociated with the piece of building equipment. Other methods ofinputting a product code include scanning an RFID code, scanning a barcode, scanning a QR code, infrared tags, ultrasound tags, video, andother forms of visual ID. Once the user inputs the product code, thegraphical user interface may receive the input and acknowledge that theproduct code was correctly received. In some embodiments, the userdevice may send a request to wiring diagram generator 116 asking if dataassociated with the scanned piece of building equipment is in eithercontroller database 122 or in field device database 120. If the scannedproduct is in one of the databases, wiring diagram generator 116 maysend a message to the user device which may then display a message orpicture on the graphical user interface saying the device was found. Ifthe piece of building equipment was not found in either database, thenthe graphical user interface may display a message stating the devicewas not found. If the product code was not correctly identified, whetherbecause the code was incorrect, the reading was inaccurate, or for anyother reason, the graphical user interface may display an error messageshowing that the product code was not correctly received.

Request 303 may be a request from the user that is similar to request301. A user may be able to input a product code and receive anotification of whether the input was successful or if the user shouldtry again.

Next button 305 may be a button on the graphical user interface thatbrings a user to another display after two product codes have beencorrectly scanned and wiring diagram generator 116 has determined twoproducts associated with the product codes are in at least one ofdatabases 120 and 122. Once both product codes have been successfullyscanned, the user can press next button 305 to get to the next userinterface. In some embodiments, a user may press next button 305 afteronly inputting one product code. In these embodiments, the user may belooking for data pertaining to just one piece of building equipment andthe graphical user interface may be able to accommodate this request.Once next button 305 is pressed, a request may be sent through wirelessgateway 208 to wiring diagram generator 116 or user interface generator112 asking for data regarding two pieces of building equipment and agraphical user interface that may be able to show the pieces of buildingequipment together. In an example embodiment, a user may scan an RFIDcode for a field device and an RFID code for a controller, asking how towire the two together. After scanning the piece of building equipment,the user may press next button 305 and a request may be sent throughwireless gateway 208 to the serving system 118 which may relay therequest to wiring diagram generator 116. The request may ask forinformation and a graphical user interface displaying the field deviceswired to the controller.

Interface 312 may be a graphical user interface designed to ask a userwhich mode of operation the user would like to receive a wiringinstructions on. Interface 312 may include table 311 and next button309. Table 311 may be directed to the different options for modes ofoperation of a field device and a display of what type of field deviceit is. For example, table 311 may include an actuator with the productname M9310-HGA-2, as shown in FIG. 3 , and options for how the actuatorcan run. In this example, the actuator may be able to operate in anincremental mode at 24V AC/DC Common and can either turn counterclockwise or clockwise. The user may be able to choose between runningthe actuator clockwise and counter clockwise. In other examples, theactuator may be able to operate in different modes and at differentvoltage levels. Further, the actuator may use a DC voltage source.Interface 312 may also include more information about the field device,such as “Device will use 2 BOs or 2 COs.” The information that isdisplayed may differ depending on the field device that is being wiredto a controller. Once the user chooses an option, the user may pressnext button 309 to send a request to user wiring diagram generator 116for information associated with the field devices, like a wiringdiagram. User interface generator 112 may receive the informationrequested at the user device and send it back to the user device.

Interface 316 may show the different inputs and outputs that the fielddevice has in a list form 319 and give the user an opportunity to pickwhich outputs and inputs to use when wiring a controller to a fielddevice. The outputs and inputs that the user selects may be displayed ina graphical user interface displaying the controller connected to thefield device. Once the user selects the inputs and outputs, the user maybe able to select a generate wiring button 317 to show the user how towire the controller to the field device. Once generate wiring button 317is pressed, the user device may send another request to wiring diagramgenerator 112 asking for wiring and data information that correspond tothe user selected inputs. Wiring diagram generator 116 may retrieve thisinformation and send back a graphical user interface through userinterface generator 112 showing the requested information.

Interface 318 is another embodiment of a display giving a user theoption of determining how the user wants to wire a field device to acontroller to achieve a certain mode of operation. Interface 318 mayinclude a graphic 323 with a picture showing the different wiringconfiguration types instead of a table as shown in interface 316. Inthis embodiment, the user may select how the user wants the field deviceto operate by pressing on one of the wiring options, such as counterclockwise or clockwise. Once the user has selected a mode of operation,the user may receive a graphical user interface showing the user how towire the field devices to the controller by pressing on a generatewiring button 321. Once generate wiring button 321 is pressed, the userdevice may send another request to wiring diagram generator 112 askingfor wiring and data information that correspond to the user selectedinputs. Wiring diagram generator 116 may retrieve this information andsend back a graphical user interface through user interface generator112 showing the requested information.

FIG. 4 is a flowchart of a process 400 for uploading wiring diagrams andequipment data pertaining to building equipment to an installationmanagement system and sending and displaying them on a user device,according to some embodiments. Process 400 may include more or feweroperations than are described here, this disclosure is not meant to belimiting. Process 400 may be conducted using components shown anddiscussed in reference to FIGS. 1-3 . Process 400 includes operations402, 404, 406, 408, 410, 412, 414. Each operation is directed towardsreceiving a request for a graphical wiring diagram between two pieces ofbuilding equipment, such as a controller and a field device; determininga wiring configuration for the two pieces of building equipment,generating a graphical user interface; and sending the graphical userinterface to the user device that sent the request.

In operation 402, the installation management system may receive arequest from a user device asking for a wiring diagram between twopieces of building equipment. The request may also ask for otherinformation pertaining to each piece of building equipment. In operation404, the building equipment locater identifies each piece of buildingequipment in the databases. If one or both of the pieces of buildingequipment are not in either database, the installation management systemmay send a message to the requesting user device stating that the pieceof building equipment is not in the system.

In operation 406, a controller identifier and a field device identifiermay identify each possible wiring configuration for the pieces ofbuilding equipment in the request. In operation 408, a wiringconfiguration generator may match compatible wiring configurationsbetween the pieces of building equipment and may create a list includingeach matched wiring configuration with information associated with eachmatch. The information may pertain to the physical components of thepieces of building equipment, the wiring configurations, how each pieceof building equipment may operate under each wiring configuration, etc.In operation 410, if the wiring configuration generator does not find amatching wiring diagram between the two pieces of building equipment,the installation management system sends an error message back to theuser device indicating that the pieces of building equipment cannot bewired together.

In operation 412, if the wiring configuration generator finds at leastone match, the graphical wiring diagram generator may generate agraphical wiring diagram displaying the two pieces of building equipmentwired together. The graphical wiring diagram may include otherinformation related to the pieces of building equipment or the wiringconfiguration. In operation 414, the user interface generator maygenerate a user-interactive user interface. The user-interactivegraphical user interface may allow a user to obtain further informationabout each piece of building equipment and the wiring diagram bypressing on spots within the graphical user interface. In someembodiments, the graphical user interface includes all the informationabout each piece of building equipment and each wiring configurationwhen it is initially sent to the user device. In these embodiments, theuser interface can retrieve information from the user device. In someembodiments, only the initially selected wiring configuration andbuilding equipment information is sent to the user device, so the userdevice can send another request to the installation management system toobtain a new graphical user interface.

In some embodiments, process 400 includes an operation (not shown) wherea controller provider uploads controller information, such as a wiringdiagram, to a network. When uploading the controller diagram, thecontroller provider may manually tag the wiring diagram with tagsdescribing the controller and different wiring configurations for thecontroller. The process may also include an operation where a fielddevice provider uploads a wiring diagram for a field device along withinformation about the field device, and tags the wiring diagram andinformation with similar tags. When the wiring configurator matches therequested controller with the requested field device, the wiringconfigurator can match the tags of the wiring configurations for eachpiece of building equipment. If the controller has a wiringconfiguration with a same tag as the field device, the wiringconfiguration generator may add the wiring configurations to a list andsend the list to the graphical wiring diagram generator.

FIG. 5 shows a wiring diagram 500 illustrating various wiringconfigurations for an actuator, according to some embodiments. Wiringdiagram 500 is shown to include different wiring configurations whichmay result in the actuator operating differently depending on the wiringconfiguration. The different wiring configurations shown in the data setconfigure the actuator to operate in On/Off 24 V Applications, Floating24 V Applications, Proportional V Applications, and Proportional 24 VApplications-0 (4) to 20 mA with external resistor. This particularexample is directed to an M9310-HGA-2 Actuator. When uploaded to aserving system, the serving system can store all of the pictures, thetype of device, and the different wiring configurations in the fielddevice database. In some embodiments, wiring diagrams may be able toinclude any amount of information including any type of informationabout any type of field device or controller.

FIG. 6 shows illustrations 600 and 602 of a user device with graphicaluser interfaces generated by installation management system (not shown)of FIGS. 2-4 including wiring and configuration instructions forbuilding equipment, according to some embodiments. Illustration 600shows a picture of an example field device. Illustration 602 shows anexample graphical user interface of a wiring diagram associated with afield device.

FIG. 7 is another illustration 700 of a user device with a graphicaluser interface generated by installation management system (not shown)of FIGS. 2-4 including wiring and configuration instructions forbuilding equipment, according to some embodiments. The illustrationshows a controller wired to a field device with pointers 702 and 704pointing to the wiring configuration where the controller is wired tothe field device.

FIG. 8 is an illustration 800 of a wiring diagram of a controllerconnected to a field device, according to some embodiments. Illustration800 shows a hard copy drawing of a controller connected to a fielddevice along with details describing which wires connect the twotogether and to which inputs. Illustration 800 also shows a descriptionwhich controller is connected to which field device and how they areconnected (Switch High, EXT Sourced).

FIG. 9 is an illustration 900 of a user device 902 connected to aproduct database 908 having a wiring configuration connecting acontroller with a field device, according to some embodiments.Illustration 900 shows user device 902 at an interface where a user caninput two product codes to receive a wiring configuration. Illustration900 also includes signal symbol 904 indicating the user device's 902signal strength when contacting a wireless gateway 906. User device's902 contact with wireless gateway 906 is illustrated with a contactsymbol 905. After contacting wireless gateway 906, user device 902 canaccess a product database 908 holding different wiring configurations.An example wiring configuration between a controller and a field deviceis shown in wiring configuration 910.

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems, and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media may be able to beany available media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium.

Combinations of the above are also included within the scope ofmachine-readable media. Machine-executable instructions include, forexample, instructions and data which cause a general purpose computer,special purpose computer, or special purpose processing machines toperform a certain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A method for guided installation of buildingequipment, the method comprising: receiving, from a user device, arequest for a wiring diagram for wiring a first piece of buildingequipment to a second piece of building equipment, the requestindicating that a user selected the first piece of building equipmentand the second piece of building equipment using a first graphical userinterface at the user device; responsive to the receiving the request,identifying one or more first wiring configurations associated with thefirst piece of building equipment and one or more second wiringconfigurations associated with the second piece of building equipment,the identified one or more first wiring configurations and one or moresecond wiring configurations being among a plurality of wiringconfigurations stored in a memory prior to the receiving the request;responsive to the receiving the request, generating a list of potentialwiring configurations by (1) retrieving the one or more first wiringconfigurations and the one or more second wiring configurations from thememory, (2) comparing the one or more first wiring configurations withthe one or more second wiring configurations, and (3) identifying afirst wiring configuration of the one or more first wiringconfigurations that is compatible with a second wiring configuration ofthe one or more second wiring configurations based on the comparison;automatically selecting, from the generated list, an equipment-specificwiring configuration for wiring the first piece of building equipment tothe second piece of building equipment; and providing a second graphicaluser interface to the user device, the second graphical user interfacecomprising a wiring diagram illustrating the equipment-specific wiringconfiguration wherein the providing the second graphical user interfaceincludes at least one of transmitting the wiring diagram over a networkto the user device for display or displaying the wiring diagram at theuser device.
 2. The method of claim 1, wherein the request comprises anidentification of a mode of operation of the second piece of buildingequipment, and wherein the automatically selecting theequipment-specific wiring configuration comprises selecting theequipment-specific wiring configuration based on the mode of operation,wherein the wiring diagram comprises a picture of wire elementsconnecting to input elements, wherein the wiring diagram comprises oneor more parts that, when displayed at the user device and selected bythe user, cause display of additional information.
 3. The method ofclaim 1, wherein the one or more first wiring configurations correspondto wiring the first piece of building equipment and the one or moresecond wiring configurations correspond to wiring the second piece ofbuilding equipment, and further comprising: storing the one or morefirst wiring configurations and the one or more second wiringconfigurations in the memory prior to receiving the request, wherein thegenerating the list of potential wiring configurations is performedresponsive to the receiving the request and further comprises retrievingthe one or more first wiring configurations and the one or more secondwiring configurations from the memory.
 4. The method of claim 1, furthercomprising obtaining a first equipment identifier from the first pieceof the building equipment and obtaining a second equipment identifierfrom the second piece of building equipment, the first and secondequipment identifiers comprising at least one of an RFID code, a UPCcode, a CPC binary bar code, a POSTNET, or a QR code.
 5. The method ofclaim 1, further comprising receiving a second request from the userdevice for a new wiring configuration associated with the first piece ofbuilding equipment and the second piece of building equipment based onan input from a user; and configuring a new graphical user interfacebased on the new wiring configuration.
 6. The method of claim 1, whereinthe generating the list of potential wiring configurations comprisesgenerating the list to have a plurality of potential wiringconfigurations, and further comprising: sending each of the plurality ofpotential wiring configurations of the generated list to the userdevice.
 7. The method of claim 1, further comprising tagging each of theone or more first wiring configurations with an identifier of the firstpiece of building equipment and tagging each of the one or more secondwiring configurations with an identifier of the second piece of buildingequipment.
 8. The method of claim 1, wherein the comparing the one ormore first wiring configurations with the one or more second wiringconfigurations comprises comparing tags of the one or more first wiringconfigurations with tags of the one or more second wiring configurationsand matching the first wiring configuration with the second wiringconfiguration responsive to the first wiring configuration and thesecond wiring configuration having matching tags.
 9. The method of claim1, wherein the identifying the one or more first wiring configurationsand the one or more second configurations comprises identifying, from adatabase comprising controller diagrams and a database comprising fielddevice data, one or more wiring configurations that have been taggedwith an identifier representing the first piece of building equipmentand one or more wiring configurations that have been tagged with anidentifier representing the second piece of building equipment.
 10. Themethod of claim 1, further comprising displaying, via the user device, auser interface that prompts a user to select a first wiring connectionon the first piece of building equipment to wire to a second wiringconnection on the second piece of building equipment; wherein theautomatically selecting the equipment-specific wiring configurationcomprises selecting a wiring configuration in which the first wiringconnection on the first piece of building equipment is wired to thesecond wiring connection on the second piece of building equipment. 11.An installation management system for building equipment, saidinstallation management system comprising one or more processorscommunicatively coupled to one or more memory devices, said installationmanagement system configured to: receive, from a user device, a requestfor a wiring diagram for wiring a first piece of building equipment to asecond piece of building equipment, the request indicating that a userselected the first piece of building equipment and the second piece ofbuilding equipment using a first graphical user interface at the userdevice; responsive to the receiving the request, identify one or morefirst wiring configurations associated with the first piece of buildingequipment and one or more second wiring configurations associated withthe second piece of building equipment, the identified one or more firstwiring configurations and one or more second wiring configurations beingamong a plurality of wiring configurations stored in a memory prior tothe receiving the request; responsive to the receiving the request,generate a list of potential wiring configurations by (1) retrieving theone or more first wiring configurations and the one or more secondwiring configurations from the memory, (2) comparing the one or morefirst wiring configurations with the one or more second wiringconfigurations, and (3) identifying a first wiring configuration of theone or more first wiring configurations that is compatible with a secondwiring configuration of the one or more second wiring configurationsbased on the comparison; automatically select, from the generated list,an equipment-specific wiring configuration for wiring the first piece ofbuilding equipment to the second piece of building equipment; andprovide a second graphical user interface to the user device, the secondgraphical user interface comprising a wiring diagram illustrating theequipment-specific wiring configuration, the wiring diagram including apicture of wire elements connecting to input elements, wherein thewiring diagram includes one or more parts that, when displayed at theuser device and selected by the user, cause dis play of additionalinformation.
 12. The installation management system of claim 11, whereinthe first piece of building equipment is a controller and the secondpiece of building equipment is a field device.
 13. The installationmanagement system of claim 11, wherein the request comprises a firstequipment identifier identifying the first piece of building equipmentand a second equipment identifier identifying the second piece ofbuilding equipment.
 14. The installation management system of claim 13,wherein the installation management system is further configured toobtain the first equipment identifier from the first piece of buildingequipment and obtain the second equipment identifier from the secondpiece of building equipment, the first and second equipment identifierscomprising at least one of an RFID code, a UPC code, a CPC binary barcode, a POSTNET, or a QR code.
 15. The installation management system ofclaim 11, wherein the installation management system is furtherconfigured to receive a second request from the user device for newwiring configurations associated with the first piece of buildingequipment and the second piece of building equipment based on an inputfrom a user and configure a new graphical user interface based on thenew wiring configurations.
 16. The installation management system ofclaim 11, wherein the installation management system is furtherconfigured to tag each of the one or more first wiring configurationswith an identifier of the first piece of building equipment and tag eachof the one or more second wiring configurations with an identifier ofthe second piece of building equipment.
 17. A non-transitorycomputer-readable storage medium having computer-executable instructionsembodied thereon, wherein when executed by at least one processor, thecomputer-executable instructions cause the at least one processor to:receive, from a user device, a request for a wiring diagram for wiring afirst piece of building equipment to a second piece of buildingequipment, the request indicating that a user selected the first pieceof building equipment and the second piece of building equipment using afirst graphical user interface at the user device; responsive to thereceiving the request, identify one or more first wiring configurationsassociated with the first piece of building equipment and one or moresecond wiring configurations associated with the second piece ofbuilding equipment, the identified one or more first wiringconfigurations and one or more second wiring configurations being amonga plurality of wiring configurations stored in a memory prior to thereceiving the request; responsive to the receiving the request, generatea list of potential wiring configurations by (1) retrieving the one ormore first wiring configurations and the one or more second wiringconfigurations from the memory, (2) comparing the one or more firstwiring configurations with the one or more second wiring configurations,and (3) identifying a first wiring configuration of the one or morefirst wiring configurations that is compatible with a second wiringconfiguration of the one or more second wiring configurations based onthe comparison; automatically select, from the generated list, anequipment-specific wiring configuration for wiring the first piece ofbuilding equipment to the second piece of building equipment; andprovide a second graphical user interface to the user device, the secondgraphical user interface comprising a wiring diagram illustrating theequipment-specific wiring configuration wherein the providing the secondgraphical user interface includes at least one of transmitting thewiring diagram over a network to the user device for display ordisplaying the wiring diagram at the user device.
 18. Thecomputer-readable storage medium of claim 17, wherein the first piece ofbuilding equipment is a controller and the second piece of buildingequipment is a field device.
 19. The computer-readable storage medium ofclaim 17, wherein the computer-executable instructions further cause theprocessor to obtain a first equipment identifier from the first piece ofbuilding equipment and obtain a second equipment identifier from thesecond piece of building equipment, the first and second equipmentidentifiers comprising at least one of an RFID code, a UPC code, a CPCbinary bar code, a POSTNET, or a QR code.
 20. The computer-readablestorage medium of claim 17, wherein the computer-executable instructionsfurther cause the processor to tag each of the one or more first wiringconfigurations with an identifier of the first piece of buildingequipment and tag each of the one or more second wiring configurationswith an identifier of the second piece of building equipment.